Project Attributes dialog

Many attributes can be set globally during Project Setup. For subsequent changes in global attributes, it is easiest to checkmark all Projects and then choose Project > Attributes of Checkmarked Projects... (after making sure the PDFs are writable).
All settings described here are made in the Project Attributes dialog.
File Types
Generally, you would include at least the following file types in a SNiFF+ Java project:

- Java -- these are the Java source files (

*.java )
- HTML -- HTML files to embed applets
- Visaj_Project -- project files for the integrated Visaj GUI builder.
Project Targets
This section describes each field in the Build Options > Project Targets > Java tab.

- If you have opened the Project Attributes dialog for multiple targets, make sure the correct project for the corresponding target is selected in the Project List at the right of the dialog.
- For related technical information, see also Compilation, Compiler Options and Execution.
- Because of changes in the behavior of the JDK appletviewer between JDK 1.1.x and JDK 1.2, alternative procedures are described below.
To avoid confusion, first check which JDK version you are using, then follow the steps under the appropriate heading. Ignore everything under the non-applicable heading.

If you're using JDK 1.1.x
If you're using JDK 1.2, ignore everything below and continue with If you're using JDK 1.2.

In the Application Class field, enter the name of the class implementing the

main method in the following form: classname .

| Note
| For GUI entries, never use fully qualified class names. Simply enter the class names without qualification or extension. Enter HTML file names and library files with extension.

- In the Applet Class(es) field, enter the name(s) of the classes implementing an
init method in the following form: classname1 classname2 ... (use a space as separator). Note: These classes will only be generated if you enter a name for the HTML file (see below).
In the HTML File field, enter the name for the HTML file that embeds the applet(s) in the following form: filename.html (with extension). The file will be automatically generated in the selected project directory by SNiFF+.
In the Library (JAR) field, enter a name (with extension) for a library if you want to build one. The library will be built at the package root to ensure correct package scope.
In the + JAR Filelist field, enter a list of files that you want archived e.g., *.html *.class test.doc separated by blanks. A specific project directory path can also be entered if you want to archive only a part of the project, e.g., utilities/*.class . Note that the path must point into the project.
In the Target class(es) field enter the name(s) of individual classes you might want to compile, e.g., to use as beans, in the following form: classname1 classname2 ... (use a space as separator). The classes must be in the currently selected project.
If you have projects with classes that are not explicitly referenced by targets, enter their names in this field to make sure that these files are also recompiled if they are out of date.
Your next step is to check the structural information for compilation.
Select Build Options > Build Structure > Java tab, and continue with Build Structure.
If you're using JDK 1.2
If you're using JDK 1.1.x, ignore everything below and continue with If you're using JDK 1.1.x.

In the Application Class field, enter the name of the class implementing the

main method in the following form: classname .

| Note
| For GUI entries, never use fully qualified class names. Simply enter the class names without qualification or extension. Enter HTML file names and library files with extension.

- Leave the Applet Class(es) field blank.
  This feature does not work if you are using JDK 1.2. In this case, enter any applet classes the Target class(es) field (see below). See also Upgrading from JDK 1.1.x to JDK 1.2.x.
- Leave the HTML File field blank.
  This feature does not work if you are using JDK 1.2. See also Upgrading from JDK 1.1.x to JDK 1.2.x.
- In the Library (JAR) field, enter a name (with extension) for a library if you want to build one. The library will be built at the package root to ensure correct package scope.
- In the + JAR Filelist field, enter a list of files that you want archived e.g.,
*.html *.class test.doc separated by blanks. A specific project directory path can also be entered if you want archive only a part of the project, e.g., utilities/*.class . Note that the path must point into the project.
In the Target class(es) field enter the name(s) of individual classes you might want to compile, e.g., to use as beans, and also of applet classes (where init is implemented) in the following form: classname1 classname2 ... (use a space as separator). The classes must be in the currently selected project.
If you have projects with classes that are not explicitly referenced by targets, enter their names in this field to make sure that these files are also recompiled if they are out of date.
Your next step is to check the default structural information for compilation.
Select Build Options > Build Structure > Java tab, and continue with Build Structure.